InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-02.Z/94-02/text0140.txt

Text File | 1994-02-28 | 9.3 KB | 228 lines

I loaded up Winchat, but each time I connect to an IRC
host, I am immediately disconnected.  Can someone please
help?

Regards,

Terry
From [e-mail] Tue Feb 15 02:00:47 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA19823; Mon, 14 Feb 1994 21:26:44 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA16150; Mon, 14 Feb 1994 21:04:43 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Tue, 15 Feb 1994 02:00:47 GMT
From: [e-mail] (Ashok Aiyar)
Message-Id: <[e-mail]>
Organization: Department of Biochemistry, Case Western Reserve University
Sender: ses
References: <2jp8f8$[e-mail]>
Subject: Re: Question on Winchat

In article <2jp8f8$[e-mail]> [e-mail] writes:

>I loaded up Winchat, but each time I connect to an IRC
>host, I am immediately disconnected.  Can someone please
>help?


Yes, WinChat is a Chat client that uses Peter's CHAT protocol.
Peter's IRC client is called WINIRC.EXE

later,
Ashok
--
Ashok Aiyar                        Mail: [e-mail]
Department of Biochemistry                       Tel: [phone]
CWRU School of Medicine, Cleveland, Ohio         Fax: [phone]
MIME Enclosures OK
From [e-mail] Mon Feb 14 15:20:33 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA23447; Mon, 14 Feb 1994 21:56:43 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA23812; Mon, 14 Feb 1994 21:49:47 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Mon, 14 Feb 1994 20:20:33 EST
From: [e-mail] (Gregg Gonsalves)
Message-Id: <[e-mail]>
Organization: PANIX Public Access Internet and Unix, NYC
Sender: ses
Subject: Buggin' Out!

I've got my SLIP connection up and running using Trumpet Winsock's TCPman and
various client software (Eudora, Cello, Mosaic, HGopher, EINet
WinWAIS,Winarch, WSPing, etc.), but I keep getting general protection faults
and EMM386 errors almost everytime I am using these programs and am forced to
reboot.  Is it me or is all this software incredibly buggy?  Any suggestions
on how to make things run more smoothly?
From [e-mail] Tue Feb 15 03:09:54 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA29923; Mon, 14 Feb 1994 22:56:44 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA13902; Mon, 14 Feb 1994 22:37:16 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Tue, 15 Feb 1994 03:09:54 GMT
From: [e-mail] (Peter R. Tattam)
Message-Id: <[e-mail]>
Organization: Psychology Department, University of Tasmania
Sender: ses
References: <[e-mail]>
Subject: Re: Trumpet Winsock problem - ARP timeouts

In article <[e-mail]> [e-mail] (Karl Auer) writes:
>From: [e-mail] (Karl Auer)
>Subject: Trumpet Winsock problem - ARP timeouts
>Date: Tue, 15 Feb 1994 12:01:17
>Summary: ARP timeouts - why?
>Keywords: ARP, Trumpet, Winsock

>On two machines now, I have been unable to get Trumpet Winsock 18a to work.
>Any help greatly appreciated.

>The situation:

>3c503 network card, installed on IRQ 5 with PKTMUX over it, works fine with
>NCSA telnet and NCSA ftp. These packages also work fine under Windows, loading
>a pktdrv and unloading afterwards. I am thus convinced that the hardware and
>packet driver layers are correctly configured.

>To test the winsock, I'm using PC Eudora.

>When I run PC Eudora and ask it to (say) fetch mail, the winsock loads ok,
>finds a packet driver and gets the IP of the mail host from its local hosts
>file. It then sits there, gets four ARP timeouts, then gives up and says it
>can't connect to the host.

>Running etherfind on a local Sun shows that the ARP packets are beeing seen
>by the correct host, and it is responding.

>All parameters in TRUMPWSK.INI seem correct - in a sanity test I got two
>people who had no connection with these efforts to compare what we had
>with what we should have had and they also pronounced it correct :-)

>It _looks_ as if the Winsock can send OK but can't see incoming packets.

>It also feels as if we have overlooked something crashingly, blindingly
>obvious. At this point, any suggestions however whacky or insulting would
>be welcome.

>Regards, K.

There does seem to be some peculiarity in the ARP code.  I have noticed this
at home on my very short ethernet system (< 10 feet)  between A 486/33 & an
old 286 that I use for testing.

I'll do some more tests tonight to see if I can find out what the problem
might be.

I had suspected a faulty packet driver because I'm using the one provided with
the network card which appears to be a hacked up version of the Crynwr ne2000
driver.  Both network cards are the same so I'll try to use the standard
ne2000 Crynwr driver to see if that helps.  Also, it has been suggested that
my machines may be a little too close... I'll try a longer ethernet cable too.

I'll let you know what I find.

Peter

----------------------------------------------------------------------------
P.Tattam                                    International Phone [phone]
Programmer, Psychology Department           Australia     Phone   [phone]
University of Tasmania, Hobart, Tasmania, Australia
----------------------------------------------------------------------------
From [e-mail] Tue Feb 15 04:33:06 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA09955; Tue, 15 Feb 1994 00:26:43 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA23529; Tue, 15 Feb 1994 00:08:14 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Tue, 15 Feb 1994 04:33:06 GMT
From: [e-mail] (Peter R. Tattam)
Message-Id: <[e-mail]>
Organization: Psychology Department, University of Tasmania
Sender: ses
References: <2jorb1$[e-mail]>
Subject: Re: Win32 API and Sockets

In article <2jorb1$[e-mail]> [e-mail] (Ken Carpenter) writes:
>From: [e-mail] (Ken Carpenter)
>Subject: Win32 API and Sockets
>Date: 14 Feb 1994 13:44:01 -0800

>With the addition of true multitasking to Windows 4.0, and NT, is there really
>the same need for the asynchronous versions of the Socket routines?  Or am I
>missing the reason for these routines in the first place?

>I am about to develop an application with the Windows Sockets API for Windows
>4.0, and need to decide which set of routines to use.

>Any help on this is appreciated.

>Ken Carpenter
>Research & Development
>Delta Controls



The problem is that the winsock 1.1 spec doesn't allow threads to run in
blocking mode.  You are restricted to a single blocking thread.  This forces
you to use non-blocking sockets or async calls to do things in an MDI
application like trmptel.

Peter

----------------------------------------------------------------------------
P.Tattam                                    International Phone [phone]
Programmer, Psychology Department           Australia     Phone   [phone]
University of Tasmania, Hobart, Tasmania, Australia
----------------------------------------------------------------------------
From [e-mail] Mon Feb 14 19:27:19 1994
Received: from NOC4.DCCS.UPENN.EDU by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA10013; Tue, 15 Feb 1994 00:27:22 -0500
Received: from POBOX.UPENN.EDU by noc4.dccs.upenn.edu
    id AA14006; Tue, 15 Feb 94 00:27:20 -0500
Return-Path: <[e-mail]>
Received: by pobox.upenn.edu
    id AA12054; Tue, 15 Feb 94 00:27:20 -0500
From: Stan Kasper <[e-mail]>
Posted-Date: Tue, 15 Feb 1994 00:27:19 -0500 (EST)
Message-Id: <[e-mail]>
Subject: WINSOCK Talk Programs
To: [e-mail]
Date: Tue, 15 Feb 1994 00:27:19 -0500 (EST)
X-Mailer: ELM [version 2.4 PL23-upenn2.7]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 824

I have been using BSDCHAT and WINTALK over TRUMPET winsock SLIP connection
and have been having trouble with WINTALK but not BSDCHAT.  What happens with
WINTALK is that when I try  to CONFIGURE/TALK it bombs and takes the TRUMPET
WINSOCK with it.  But BSDCHAT seems to not have any problem.

Now there are some things I like about WINTALK that make it more desirable.
Is there something I need to do to configure it properly?  I have MTU set
to 255 and RWIN set to 2048.  I am using #18 for WINSOCK.  I know there
has been alot of traffic on this.  Can someone set us straght on a good
'TALK' setup for WINSOCK?

BTW.  Traffic for this LISTSERV has been off.  Whats up?  Is it my end?

-Stan Kasper                                     SMASHING PUMPKINS!!!
University of Pennsylvania                       SIAMESE DREAM